components/box/actions/upload-file-version/upload-file-version.mjs (2)

61-70: Remove unused params to reduce confusion.
createdAt and parentId aren’t defined props for version upload; pass only what’s used.

-    const {
-      file, fileId, createdAt, modifiedAt, fileName, parentId,
-    } = this;
+    const {
+      file, fileId, modifiedAt, fileName,
+    } = this;
@@
-    const data = await this.getFileUploadBody({
-      file,
-      createdAt,
-      modifiedAt,
-      fileName,
-      parentId,
-    });
+    const data = await this.getFileUploadBody({
+      file,
+      modifiedAt,
+      fileName,
+    });

---

75-77: Prefer FormData helpers over private _boundary.
Use getHeaders() or getBoundary() when available.

-      headers: {
-        "Content-Type": `multipart/form-data; boundary=${data._boundary}`,
-      },
+      headers: data.getHeaders?.() ?? {
+        "Content-Type": `multipart/form-data; boundary=${data.getBoundary?.() ?? data._boundary}`,
+      },

components/box/sources/new-file/new-file.mjs (1)

6-6: Polish description grammar.
Minor wording tweak for clarity.

-  description: "Emit new event when a new file uploaded on a target. [See the documentation](https://developer.box.com/reference/post-webhooks)",
+  description: "Emit an event when a new file is uploaded. [See the documentation](https://developer.box.com/reference/post-webhooks)",

components/box/sources/new-folder/new-folder.mjs (1)

6-6: Polish description grammar.
Minor wording tweak for clarity.

-  description: "Emit new event when a new folder created on a target. [See the documentation](https://developer.box.com/reference/post-webhooks)",
+  description: "Emit an event when a new folder is created. [See the documentation](https://developer.box.com/reference/post-webhooks)",

components/box/actions/upload-file/upload-file.mjs (1)

65-69: Prefer FormData helpers over private _boundary.
Align with best practice and future-proof boundary handling.

-      headers: {
-        "Content-Type": `multipart/form-data; boundary=${data._boundary}`,
-      },
+      headers: data.getHeaders?.() ?? {
+        "Content-Type": `multipart/form-data; boundary=${data.getBoundary?.() ?? data._boundary}`,
+      },

components/apify/common/constants.mjs (1)

1-3: Nit: document the hard-coded WCC actor ID

Add a brief comment (actor name, link) so future changes to the WCC actor are easier to track.

-export const WCC_ACTOR_ID = "aYG0l9s7dbB7j3gbS";
+// Web Content Crawler (official Apify actor). Update if the canonical actor changes.
+export const WCC_ACTOR_ID = "aYG0l9s7dbB7j3gbS";

components/apify/actions/scrape-single-url/scrape-single-url.mjs (1)

67-73: Tighten dataset read and handle empty results

Limit to 1 item and fail clearly when nothing is extracted. Also surface the console URL in the summary for quick triage.

-    const { items } = await this.apify.listDatasetItems({
-      datasetId: defaultDatasetId,
-    });
+    const { items } = await this.apify.listDatasetItems({
+      datasetId: defaultDatasetId,
+      limit: 1,
+      offset: 0,
+    });
 
-    $.export("$summary", "Run of Web Content Crawler finished successfully.");
-    return items[0];
+    if (!items?.length) {
+      throw new Error("No result extracted for the provided URL.");
+    }
+    $.export("$summary", `Web Content Crawler run succeeded. Inspect: ${consoleUrl}`);
+    return items[0];

components/apify/actions/get-dataset-items/get-dataset-items.mjs (2)

61-72: Optional: avoid over-fetching when limit is small.

Dynamically reduce page size to the remaining budget.

Apply:

-    do {
-      const { items } = await this.apify.listDatasetItems({
+    do {
+      const remaining = Number.isInteger(this.limit) ? Math.max(this.limit - results.length, 0) : LIMIT;
+      params.limit = Math.min(LIMIT, remaining || LIMIT);
+      const { items } = await this.apify.listDatasetItems({
         datasetId: this.datasetId,
         params,
       });
       results.push(...items);
-      if (results.length >= this.limit) {
+      if (Number.isInteger(this.limit) && results.length >= this.limit) {
         break;
       }
       total = items?.length;
       params.offset += LIMIT;
     } while (total);

---

74-76: Guard trim when limit is unset.

Only trim when limit is a number.

Apply:

-    if (results.length > this.limit) {
-      results.length = this.limit;
-    }
+    if (Number.isInteger(this.limit) && results.length > this.limit) {
+      results.length = this.limit;
+    }

components/apify/actions/set-key-value-store-record/set-key-value-store-record.mjs (2)

12-24: Required store/key: good; also validate non-empty key.

Add a simple runtime check to prevent empty or whitespace-only keys.

Apply:

   async run({ $ }) {
+    if (!this.key || !String(this.key).trim()) {
+      throw new Error("Key is required and cannot be empty.");
+    }

---

33-76: Robust value inference; consider binary case.

If consumers pass a Buffer or base64 blob, you may want to detect and set contentType: application/octet-stream.

Example enhancement (outside current diff scope):

if (typeof Buffer !== "undefined" && Buffer.isBuffer(input)) {
  return { data: input, contentType: "application/octet-stream", mode: "binary" };
}

components/apify/actions/run-actor/run-actor.mjs (1)

187-193: Avoid “undefined ...” in descriptions.

When value.description is missing, concatenations produce “undefined ...”.

Apply:

         props[key] = {
           type: this.getType(value.type),
           label: value.title,
-          description: value.description,
+          description: value.description || "",
           optional: !requiredProps.includes(key),
         };

(With this change, later += appends are safe.)

Also applies to: 200-205, 221-222

components/apify/apify.app.mjs (2)

134-139: Grammar nit: clarify the offset description.

Apply:

-      description: "The number records to skip before returning results",
+      description: "The number of records to skip before returning results",

---

142-154: Optional: cache the ApifyClient instance.

Avoid recreating the client on every call.

Example:

-  _client() {
-    return new ApifyClient({
+  _client() {
+    if (!this.__apifyClient) {
+      this.__apifyClient = new ApifyClient({
         token: this.$auth.api_token,
         requestInterceptors: [
           (config) => ({
             ...config,
             headers: {
               ...(config.headers || {}),
               "x-apify-integration-platform": "pipedream",
             },
           }),
         ],
-    });
+      });
+    }
+    return this.__apifyClient;
   },

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

components/apify/actions/scrape-single-url/scrape-single-url.mjs (3)

68-70: Limit dataset fetch and return clean items.
Avoid fetching more than needed and prefer cleaned items.

Apply this diff:

-    const { items } = await this.apify.listDatasetItems({
-      datasetId: defaultDatasetId,
-    });
+    const { items } = await this.apify.listDatasetItems({
+      datasetId: defaultDatasetId,
+      params: { limit: 1, clean: true },
+    });

---

72-73: Handle empty dataset explicitly.
Avoid returning undefined when no items are produced.

Apply this diff:

-    $.export("$summary", "Run of Web Content Crawler finished successfully.");
-    return items[0];
+    const item = items && items[0];
+    if (!item) {
+      throw new Error(`No dataset items returned for URL: ${this.url}. Inspect the run: ${consoleUrl}.`);
+    }
+    $.export("$summary", "Run of Web Content Crawler finished successfully.");
+    return item;

---

8-8: Update description to reflect current behavior.
The action now returns the first dataset item, not “content as HTML”.

Apply this diff:

-  description: "Executes a scraper on a specific website and returns its content as HTML. This action is perfect for extracting content from a single page. [See the documentation](https://docs.apify.com/sdk/js/docs/examples/crawl-single-url)",
+  description: "Runs the Web Content Crawler on a single URL and returns the first item from its dataset after the run completes. [See the documentation](https://docs.apify.com/sdk/js/docs/examples/crawl-single-url)",

components/apify/actions/run-actor/run-actor.mjs (4)

135-144: Exclude non-schema props from the actor input (e.g., actorSource).

Unknown props can leak into the run input. Filter by schema keys and/or exclude at destructure.

Apply:

       for (const [
         key,
         value,
       ] of Object.entries(data)) {
-        const editor = properties[key]?.editor || "hidden";
+        if (!properties[key]) continue;
+        const editor = properties[key].editor || "hidden";
         newData[key] = Array.isArray(value)
           ? value.map((item) => this.setValue(editor, item))
           : value;
       }

Also remove actorSource from the residual data:

   async run({ $ }) {
     const {
       apify,
       actorId,
+      actorSource,
       buildTag,

Also applies to: 256-268

---

199-201: Prevent “undefined …” in descriptions when schema lacks description.

String concatenation on undefined yields “undefined …”.

Apply:

-          if (value.unit) {
-            props[key].description += ` Unit: ${value.unit}.`;
-          }
+          if (value.unit) {
+            props[key].description = `${props[key].description ?? ""} Unit: ${value.unit}.`;
+          }

-          props[key].description += ` Default: \`${JSON.stringify(defaultValue)}\``;
+          props[key].description = `${props[key].description ?? ""} Default: \`${JSON.stringify(defaultValue)}\``;

Also applies to: 221-221

---

146-153: Support enums without titles.

Fallback labels to enum values when enumTitles are absent.

Apply:

   prepareOptions(value) {
-      if (value.enum && value.enumTitles) {
+      if (value.enum && value.enumTitles) {
         return value.enum.map((val, i) => ({
           value: val,
           label: value.enumTitles[i],
         }));
+      } else if (value.enum) {
+        return value.enum.map((val) => ({
+          value: val,
+          label: String(val),
+        }));
       }
     },

---

4-4: Default webhook event types to terminal events when not provided.

Improves UX and aligns with Apify guidance.

Apply:

-import { WEBHOOK_EVENT_TYPES } from "@apify/consts";
+import { WEBHOOK_EVENT_TYPES, WEBHOOK_EVENT_TYPE_GROUPS } from "@apify/consts";

       ...(webhook && {
         webhooks: [
           {
-            eventTypes,
+            eventTypes: (eventTypes && eventTypes.length)
+              ? eventTypes
+              : WEBHOOK_EVENT_TYPE_GROUPS.ACTOR_RUN_TERMINAL,
             requestUrl: webhook,
           },
         ],
       }),

Also applies to: 317-324

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

Learnt from: matyascimbulka
PR: PipedreamHQ/pipedream#18308
File: components/apify/sources/common/base.mjs:17-0
Timestamp: 2025-09-12T08:28:06.736Z
Learning: WEBHOOK_EVENT_TYPE_GROUPS.ACTOR_RUN_TERMINAL from apify/consts is an array containing all terminal Actor run event types: ["ACTOR.RUN.SUCCEEDED", "ACTOR.RUN.FAILED", "ACTOR.RUN.ABORTED", "ACTOR.RUN.TIMED_OUT"]. It should be used directly in the eventTypes field when creating webhooks for future-proofing.